Data transmission method and apparatus, and computer readable storage medium

ABSTRACT

Provided are a data transmission method, apparatus and computer readable storage medium. The method includes: in a case where a terminal is in a connected state, receiving, by the terminal, a physical downlink control channel command sent by a base station, acquiring an non-competitive resource allocated to the terminal by the base station from the physical downlink control channel command, initiating a random access by using a random access preamble corresponding to the non-competitive resource; and receiving, by the terminal, a random access response sent by the base station, and in response to determining that the random access response carries indication information for simultaneously sending downlink data, receiving, by the terminal, the downlink data.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/738,180, filed on May 6, 2022, which is a continuation of U.S. patentapplication Ser. No. 16/638,311, filed on Feb. 11, 2020, which is theU.S National Stage of International Patent Application NumberPCT/CN2018/100247, filed on Aug. 13, 2018, which claims priority toChinese Patent Application Number 201710687283.5, filed on Aug. 11,2017, the disclosures of which are incorporated herein by reference intheir entireties.

TECHNICAL FIELD

The present application relates to communications and, for example, to adata transmission method and apparatus, and a computer readable storagemedium.

BACKGROUND

In a machine to machine (M2M) communication system, energy saving of auser equipment (UE) is crucial. In the related art, when the UE is in anRRC_IDLE state and data to be sent comes, the UE first triggers a randomaccess procedure to setup or resume a radio resource control (RRC)connection with a network, and the UE may send the data to the basestation along with an RRC-connection setup complete message or anRRC-resume complete message at the earliest. Then, the UE will remain inan RRC_CONNECTED state for a period of time, waiting for the basestation to release the UE. When the UE is in the RRC_CONNECTED state andhas data to send, the UE may need to initiate a random access firstsince losing time synchronization or having no uplink resource, and sendthe data to the base station after the random access process iscompleted.

SUMMARY

The following is a summary of the subject matter described herein indetail. This summary is not intended to limit the scope of the claims.

An embodiment of the present application provides a data transmissionmethod and apparatus, and a computer readable storage medium.

An embodiment of the present application provides a data transmissionmethod. The method includes sending, by a terminal, a random accesspreamble to a base station, and receiving a random access response sentby the base station; and sending, by a terminal, a first request messagecarrying uplink data to the base station.

An embodiment of the present application provides a data transmissionapparatus, which includes a memory and a processor, where the memorystores a program, and the data transmission method described above isperformed when the program is read and executed by the processor.

An embodiment of the present application provides a computer-readablestorage medium storing at least one program, where the at least oneprogram is executable by at least one processor, to perform the datatransmission method described above.

An embodiment of the present application provides a data transmissionmethod. The method includes receiving, by a base station, a randomaccess prefix sent by a terminal, and sending a random access responseto the terminal; and

-   -   receiving, by the base station, a first request message carrying        uplink data sent by the terminal.

In an embodiment, the first S1 interface message is one of: an initialuser equipment (UE) message, a UE context resume request message, anuplink non-access stratum (NAS) transport message, a path switch requestmessage or a newly-defined S1 interface message;

-   -   the second S1 interface message is one of: a connection setup        indication message, a UE context resume response message, a        downlink NAS transport message, a path switch request        acknowledgement message and a newly-defined S1 interface        message.

An embodiment of the present application provides a data transmissionapparatus, the apparatus includes a memory and a processor, where thememory stores a program, and the data transmission method describedabove is performed when the program is read and executed by theprocessor.

An embodiment of the present application provides a computer-readablestorage medium storing at least one program, where the at least oneprogram is executable by at least one processor, to perform the datatransmission method described above.

An embodiment of the present application provides a data transmissionmethod, the method includes sending a first request message to a basestation in a random access process in a case where the terminal is in anidle state, receiving a second response message sent by the basestation, and acquiring downlink data in the second response message.

An embodiment of the present application provides a data transmissionapparatus, which includes a memory and a processor, where the memorystores a program which, when read and executed by the processor, causesthe processor to:

-   -   send a first request message to a base station in a random        access process in a case where the terminal is in an idle state,        receive a second response message sent by the base station, and        acquire downlink data in the second response message.

An embodiment of the present application provides a computer-readablestorage medium, which stores at least one program, where at least oneprocessor is capable of executing the at least one program to implement:sending a first request message to a base station in a random accessprocess in a case where the terminal is in an idle state, receiving asecond response message sent by the base station, and acquiring downlinkdata in the second response message.

An embodiment of the present application provides a data transmissionmethod, the method includes in a process of performing a random accessin a case where a terminal is in an idle state, receiving, by a basestation, a first request message sent by the terminal, in response todetermining that the base station has downlink data required to be sentto the terminal, carrying, by the base station, the downlink data at thetime of sending the second response message to the terminal.

An embodiment of the present application provides a data transmissionapparatus. The apparatus includes a memory and a processor, where thememory stores a program which, when read and executed by the processor,performs the data transmission method.

An embodiment of the present application provides a computer-readablestorage medium storing at least one program, where the at least oneprogram is executable by at least one processor to perform the datatransmission method described above.

An embodiment of the present application provides data transmissionmethod. The method includes in a process of performing a random accessin a case where a terminal is in an idle state, sending, by a networkside, a second S1 interface message to a base station after receiving afirst SI interface message sent by the base station, where the second S1interface message carries downlink data required to be sent to theterminal.

An embodiment of the present application provides data transmissionapparatus. The apparatus includes a memory and a processor, where thememory stores a program, and the data transmission method describedabove is performed when the program is read and executed by theprocessor.

An embodiment of the present application provides a computer-readablestorage medium storing at least one program, where the at least oneprogram is executable by at least one processor, to perform the datatransmission method described above.

An embodiment of the present application provides data transmissionmethod. The method includes: in a case where a terminal is in aconnected state, receiving, by the terminal, a physical downlink controlchannel command sent by a base station, acquiring an non-competitiveresource allocated to the terminal by the base station from the physicaldownlink control channel command, initiating a random access by using arandom access prefix corresponding to the non-competitive resource; andreceiving, by the terminal, a random access response sent by the basestation, and in response to determining that the random access responsecarries indication information for simultaneously sending downlink data,receiving, by the terminal, the downlink data.

An embodiment of the present application provides a data transmissionapparatus, which includes a memory and a processor, where the memorystores a program which, when read and executed by the processor, causesthe processor to:

-   -   in a case where a terminal is in a connected state, receive, by        the terminal, a physical downlink control channel command sent        by a base station, acquire an non-competitive resource allocated        to the terminal by the base station from the physical downlink        control channel command, initiate a random access by using a        random access prefix corresponding to the non-competitive        resource; and receive, by the terminal, a random access response        sent by the base station, and in response to determining that        the random access response carries indication information for        simultaneously sending downlink data, receive the downlink data.

An embodiment of the present application provides a computer-readablestorage medium, which stores at least one program, where at least oneprocessor is capable of executing the at least one program to implement:

-   -   in a case where a terminal is in a connected state, receiving,        by the terminal, a physical downlink control channel command        sent by a base station, acquiring an non-competitive resource        allocated to the terminal by the base station from the physical        downlink control channel command, initiating a random access by        using a random access prefix corresponding to the        non-competitive resource;    -   receiving a random access response sent by the base station, and        in response to determining that the random access response        carries indication information for simultaneously sending        downlink data, receiving the downlink data.

An embodiment of the present application provides a data transmissionmethod, the method includes in a case where a terminal is in a connectedstate, sending, by a base station, a physical downlink control channelcommand to the terminal, the physical downlink control channel commandcarries a non-competitive resource allocated by the base station to theterminal; and after receiving a random access initiated by the terminalusing a random access prefix corresponding to the non-competingresource, sending, by the base station, a random access response to theterminal, and the random access response carries indication informationfor simultaneously sending downlink data, and sending the downlink datasimultaneously.

An embodiment of the present application provides a data transmissionapparatus, which includes a memory and a processor, where the memorystores a program which, when read and executed by the processor, causesthe processor to:

-   -   in a case where a terminal is in a connected state, send a        physical downlink control channel command to the terminal, the        physical downlink control channel command carries a        non-competitive resource allocated by the base station to the        terminal; and after receiving a random access initiated by the        terminal using a random access prefix corresponding to the        non-competing resource, send a random access response to the        terminal, and the random access response carries indication        information for simultaneously sending downlink data, and send        the downlink data simultaneously.

An embodiment of the present application provides a computer-readablestorage medium, which stores at least one program, where at least oneprocessor is capable of executing the at least one program to implement:

-   -   in a case where a terminal is in a connected state, sending a        physical downlink control channel command to the terminal, the        physical downlink control channel command carries a        non-competitive resource allocated by the base station to the        terminal; and after receiving a random access initiated by the        terminal using a random access prefix corresponding to the        non-competing resource, sending a random access response to the        terminal, and the random access response carries indication        information for simultaneously sending downlink data, and        sending the downlink data simultaneously.

Other aspects can be understood after the drawings and the detaileddescription are read and understood.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a flowchart of implementing a random access in the relatedart;

FIG. 2 is a flowchart of implementing another random access in therelated art;

FIG. 3 is a flowchart of a data transmission method provided by anembodiment of the present application;

FIG. 4 is a flowchart of a data transmission method provided by anembodiment of the present application;

FIG. 5 is a flowchart of a data transmission method provided byembodiment one of the present application;

FIG. 6 is a flowchart of a data transmission method provided byembodiment two of the present application;

FIG. 7 is a flowchart of a data transmission method provided byembodiment three of the present application;

FIG. 8 is a flowchart of a data transmission method provided byembodiment four of the present application;

FIG. 9 is a flowchart of a data buffering method provided by embodimentfour of the present application;

FIG. 10 is a flowchart of a data transmission method provided by anembodiment of the present application (sending a second response messagefirst and then sending a first S1 interface message);

FIG. 11 is a flowchart of a data transmission method provided byembodiment six of the present application;

FIG. 12 is a flowchart of another data transmission method provided byembodiment six of the present application;

FIG. 13 is a flowchart of a data transmission method provided byembodiment seven of the present application;

FIG. 14 is a flowchart of a data transmission method provided byembodiment nine of the present application;

FIG. 15 is a flowchart of another data transmission method provided byembodiment nine of the present application;

FIG. 16 is a flowchart of a data transmission method provided byembodiment ten of the present application;

FIG. 17 is a flowchart of a data transmission method provided byembodiment eleven of the present application;

FIG. 18 is a schematic diagram of resource division provided byembodiment twelve of the present application;

FIG. 19 is a schematic diagram of another resource division provided byembodiment twelve of the present application;

FIG. 20 is a schematic diagram of another resource division provided byembodiment twelve of the present application; and

FIG. 21 is a schematic diagram of another resource division provided byembodiment twelve of the present application.

DETAILED DESCRIPTION

Embodiments of the present application will be described hereinafter indetail with reference to the drawings. The steps illustrated in theflowcharts in the drawings may be performed by a computer system such asa group of computers capable of executing instructions. Further,although logical sequences are illustrated in the flowcharts, the shownor described steps may be performed in sequences different from thosedescribed herein in some cases.

As shown in FIG. 1 , it is that in the related art a UE in an RRC_IDLEstate uses a CP scheme to upload data after a random access process,including steps 101 to 105.

In step 101, the UE sends an Msg1 message to an enhanced Node B (eNB),and carries a random access preamble.

In step 102, the eNB sends an Msg2 message to the UE, and carries arandom access response (RAR).

In step 103, the UE sends an Msg3 message to the eNB, and carries an RRCconnection request and an SAE-Temporary Mobile Subscriber Identity(S-TMSI).

In step 104, the eNB sends an Msg4 message to the UE, and carries an RRCconnection setup message.

In step 105, the UE sends an Msg5 message to the eNB, and carries an RRCconnection setup complete message and uplink data.

As shown in FIG. 2 , it is that in the related art the UE in an RRC_IDLEstate uses a UP scheme to upload data after the random access process,including steps 201 to 206.

In step 201, the UE sends the Msg1 message to the eNB and carries therandom access preamble.

In step 202, the eNB sends the Msg2 message to the UE, and carries therandom access response (RAR).

In step 203, the UE sends the Msg3 message to the eNB, and carries theRRC connection resume request and a resume ID. In step 204, the eNBsends the Msg4 message to the UE, and carries the RRC connection resumemessage. In step 205, the UE sends the Msg5 message to the eNB, andcarries the RRC connection resume complete message. In step 206, the UEsends the uplink data to the eNB. In the related art, the terminal needsto set up or resume an RRC connection when sending the uplink data, andthe terminal sends the uplink data to the base station only after theRRC connection is set up or resumed. In a large class of applications,such as a meter reading service, a static or low mobility UE each timemay only need to send one data packet, and a time interval between twodata packet sending is relatively long. In this case, the UE only sendsone data packet after entering an RRC_CONNECTED state, but needs tomaintain a period of time in the RRC_CONNECTED state to continuouslymonitor signals of the base station. After sending data once, theterminal returns to the RRC_IDLE state, or even returns to a power savemode (PSM), and reinitiates the RRC setup or resume request at the timeof sending the data next time. The data transmission method in therelated art causes unnecessary power consumption at the terminal.Therefore, embodiments of the present application provide a datatransmission scheme to improve a situation in which energy consumptionof uploading data by the terminal is relatively high in the related art.

An embodiment of the present application provides a data transmissionmethod. As shown in FIG. 3 , steps 301 to 303 are included.

In step 301, a terminal sends a random access preamble to a basestation, and receives a random access response sent by the base station.

In step 302, the terminal sends a first request message (Msg3) carryinguplink data to the base station. In a case where the terminal is in anidle state before sending the random access prefix, the method furtherincludes the step 303, after receiving a second response messagereturned by the base station and determining that a contention issuccessfully resolved, maintaining, by the terminal, the idle state,taking a temporary-radio network temporary identity (T-RNTI) allocatedby the base station carried in the random access response as acell-radio network temporary identity (C-RNTI), and retaining the C-RNTIfor a first length of time, where whether the contention is successfullyresolved is determined by a contention resolution identification carriedin the second response message. During data transmission, multipleterminals may send the same first request message to the base station,but the base station can only detect one, and the base station carriespart of information in the first request message detected in the secondresponse message. Only one terminal among multiple terminals determinesthat this second response message belongs to the terminal itself, theabove process is a process of contention resolution.

In an embodiment, the second response message carries at least one of: acontention resolution identification; high-level acknowledgementinformation for the uplink data; an uplink data failure indication; anuplink data retransmission indication; or user service data.

The first request message further carries at least one or a combinationof: indication information of whether to setup an S1 interfacepreferentially; indication information of whether to receive high-levelacknowledgement information for the uplink data; information foridentifying a mobility management entity (MME) at which the terminalregisters; terminal identification information; access stratum securityinformation; or a connection setup reason corresponding to datatransmission.

In an embodiment, after the terminal receives the second responsemessage returned by the base station and obtains the C-RNTI, the methodfurther includes: detecting, by the terminal, in a public search spaceor a search space for transmitting scheduling information of the secondresponse message, one of following information by using the C-RNTI: aphysical downlink control channel (PDCCH), uplink schedulinginformation, or downlink scheduling information.

In an embodiment, after the terminal receives the second responsemessage returned by the base station, the method further includes inresponse to determining that the terminal also needs to transmit theuplink data, the terminal needs to send the first request messagecarrying the uplink data to the base station.

Before sending the random access preamble to the base station, theterminal further selects the random access preamble or selects to sendresources of the random access preamble.

In an embodiment, sending, by the terminal, the random access preambleto the base station includes: in response to determining that theterminal satisfies a first preset condition, sending, by the terminal,the random access preamble for requesting an uplink data transmissionresource to the base station.

Sending, by the terminal, the random access preamble for requesting theuplink data transmission resource to the base station includes:selecting, by the terminal, a random access preamble from a randomaccess preamble set for requesting the uplink data transmissionresource, and sending the selected random access preamble to the basestation; or selecting, by the terminal, a random access resource from arandom access resource set for requesting the uplink data transmissionresource, and sending the random access preamble by using the selectedrandom access resource to the base station.

In an embodiment, the terminal satisfying the first preset conditionincludes at least one or a combination of: a size of uplink data to besent by the terminal is greater than a data carrying determinationthreshold; a radio link condition of the terminal satisfies a linkcondition threshold; or a service type of the uplink data to be sent bythe terminal belongs to a preset service type.

The physical downlink control channel may carry uplink schedulinginformation or downlink scheduling information.

In an embodiment, the method further includes: acquiring, by theterminal, from a system message sent by the base station, one or acombination of: a data carrying determination threshold; a linkcondition threshold; or preset service type information; where the datacarrying determination threshold includes: a data carrying determinationthreshold configured for all coverage levels, or a data carryingdetermination threshold configured for each coverage level separately.

In an embodiment, the method further includes one of: failing toreceive, by the terminal, a second response message returned by the basestation; receiving, by the terminal, the second response messagecarrying an uplink data failure indication or an uplink dataretransmission indication returned by the base station; and in responseto determining that the terminal fails to receive the random accessresponse returned by the base station, determining, by the terminal, arandom access failure and reinitiating random access.

In an embodiment, reinitiating, by the terminal, the random accessincludes: determining, by the terminal, to select one of the randomaccess preamble for requesting the uplink data transmission resource orthe random access preamble not for requesting the uplink datatransmission resource to perform the random access according to at leastone of: a number of random access failures, a serial number of eachrandom access failure; a downlink measurement obtained by the terminal;a coverage level; and a number of repetitions. The number of repetitionsis configuration information obtained by the terminal, and a downlinkmeasurement value is a reference signal received power value forexample, and of course, may be other values.

In an embodiment, the terminal reinitiates the random access accordingto one of: at an current coverage level, in response to determining thata number of random access failures of the terminal by sending the randomaccess preamble for requesting the uplink data transmission resourcereaches a threshold value for the number of random access failures,changing, by the terminal, the coverage level to a maximum coveragelevel, and sending the random access preamble not for requesting theuplink data transmission resource to perform the random access orsending the random access preamble to perform the random access; at acurrent coverage level, in response to determining that a number ofrandom access failures of the terminal by sending the random accesspreamble for requesting the uplink data transmission resource reaches athreshold value for the number of random access failures, sending, bythe terminal, the random access preamble not for requesting the uplinkdata transmission resource to perform the random access or sending therandom access preamble to perform the random access; in response todetermining that the random access still fails and the number of randomaccess failures reaches a threshold value for the number of randomaccess failures, changing, by the terminal, the coverage level to a nextcoverage level higher than the current coverage level and performing therandom access at the next coverage level in a random access manner sameas that at the current coverage level until the random access succeeds;or changing, by the terminal, the coverage level to a maximum coveragelevel and performing the random access at the maximum coverage level inthe random access manner same as that at the current coverage level; ata current coverage level, in response to determining that a number ofrandom access failures of the terminal by carrying the uplink data inthe first request message reaches a threshold value for the number ofrandom access failures, changing, by the base station, the coveragelevel to a maximum coverage level, and sending the first request messagecarrying a radio resource control (RRC) message to perform the randomaccess; at a current coverage level, in response to determining that anumber of random access failures of the terminal by sending the uplinkdata carried in the first request message reaches a threshold value forthe number of random access failures, sending, by the terminal, thefirst request message carrying an RRC message; in response todetermining that the random access still fails and the number offailures reaches a threshold value for the number of random accessfailures, changing, by the terminal, the coverage level to a nextcoverage level higher than the current coverage level and performing therandom access at the next coverage level in a random access manner sameas that at the current coverage level until the random access succeeds,or changing, by the terminal, the coverage level to a maximum coveragelevel and performing the random access at the maximum coverage level inthe random access manner same as that at the current coverage level; inresponse to determining that a number of random access failures of theterminal by sending the random access preamble for requesting the uplinkdata transmission resource reaches a threshold value for the number ofrandom access failures, sending the random access preamble not forrequesting the uplink data transmission resource to perform the randomaccess; in response to determining that a number of random accessfailures of the terminal by sending the random access preamble forrequesting the uplink data transmission resource reaches a thresholdvalue for the number of random access failures and that a referencesignal receiving power (RSRP) value measured by the terminal is in afirst predefined range, sending, by the terminal, the random accesspreamble not for requesting the uplink data transmission resource toperform the random access; in response to determining that the number ofrandom access failures of the terminal by sending the random accesspreamble for requesting the uplink data transmission resource sent bythe terminal reaches the threshold value for the number of random accessfailures and that the RSRP value measured by the terminal is in a secondpredefined range, changing, by the terminal, the coverage level to anext coverage level, and sending the random access preamble not forrequesting the uplink data transmission resource to perform the randomaccess; or sending, by the terminal, the random access preamble not forrequesting the uplink data transmission resource to perform the randomaccess after the random access failure through sending the random accesspreamble for requesting the uplink data transmission resource, sending,by the terminal, the random access preamble for requesting the uplinkdata transmission resource to perform the random access after the randomaccess failure through sending the random access preamble not forrequesting the uplink data transmission resource, and repeating theformer manner; in response to determining that a number of random accessfailures reaches a threshold value for the number of random accessfailures, changing, by the terminal, the coverage level to a nextcoverage level and performing the random access at the next coveragelevel in a random access manner same as that at the current coveragelevel until the random access succeeds, or changing, by the terminal,the coverage level to a maximum coverage level and performing the randomaccess at the maximum coverage level in the random access manner same asthat in the current coverage level.

In an embodiment, the method further includes: acquiring, by theterminal, the threshold value for the number of random access failurescorresponding to each coverage level, by receiving the system messagebroadcast by the base station or a dedicated message sent by the basestation to the terminal.

In an embodiment, before reinitiating the random access by the terminal,the method further includes: acquiring, by the terminal, operationindication information from the base station, and determining a mannerfor reinitiating the random access according to the operation indicationinformation.

In an embodiment, before performing random access by the terminal, themethod further includes: acquiring, by the terminal, operationindication information from the base station, and determining operationsperformed by the first request message carrying the uplink data afterthe random access failure according to the operation indicationinformation.

In an embodiment, before reinitiating the random access by the terminal,determining whether to terminate or suspend a power raising operationaccording to at least one of: whether a format of the first requestmessage for the random access is same as a format of the first requestmessage for a previous random access; whether a manner of sending therandom access preamble for the random access is same as a manner ofsending the random access preamble for a previous random access, wherethe manner for sending the random access preamble includes: sending therandom access preamble for requesting the uplink data transmissionresource and sending the random access preamble not for requesting theuplink data transmission resource; or a reason for a previous randomaccess failure.

In an embodiment, in a case where the terminal is in a connected statebefore sending the random access preamble, the first request messagefurther carries one or a combination of a C-RNTI, a RRC message, and arelease request indication.

In an embodiment, in the case where the terminal is in the connectedstate before sending the random access preamble, the method furtherincludes:

-   -   receiving, by the terminal, a second response message returned        by the base station, and in response to determining that a        contention is successfully resolved, autonomously releasing, by        the terminal, an RRC connection and transiting to an idle state;        or receiving, by the terminal, a second response message        returned by the base station, and in response to determining        that a contention is successfully resolved, processing, by the        terminal, an RRC release message carried in the second response        message and transit to an idle state.

In an embodiment, sending, by the terminal, the first request messagecarrying the uplink data to the base station includes: acquiring, by theterminal, indication information carried in the random access response,and in response to determining that a second preset condition issatisfied, sending, by the terminal, the first request message carryingthe uplink data to the base station.

In an embodiment, the method further includes: acquiring, by theterminal, indication information carried in the random access response,and in response to determining that a third preset condition issatisfied, sending, by the terminal, the first request message carryingan RRC message to the base station.

In an embodiment, satisfying the second preset condition is that theindication information is data amount information of a data size withuplink grant and the data size with the uplink grant is greater than anuplink grant threshold, or that the indication information indicates todirectly send the uplink data at the time of sending the first requestmessage; and satisfying the third preset condition is that theindication information is the information of the data size with theuplink grant and the data size with the uplink grant is less than orequal to the uplink grant threshold, or that the indication informationindicates to carry the RRC message at the time of sending the firstrequest message.

In an embodiment, the uplink grant threshold is one of: an uplink grantthreshold corresponding to a state of the terminal before sending therandom access preamble; or an uplink grant threshold corresponding to acoverage level at which the terminal is located and the state of theterminal before sending the random access preamble.

In an embodiment, an uplink grant threshold corresponding to theterminal in a connected state is greater than an uplink grant thresholdcorresponding to the terminal in an idle state.

In an embodiment, the method further includes: after receiving a secondresponse message returned by the base station, setting up, restoring orre-setting up, by the terminal, an RRC connection according to an RRCresponse message carried in the second response message, and transiting,by the terminal, to the connection state.

An embodiment of the present application provides a data transmissionmethod, as shown in FIG. 4 , steps 401 to 404 are included.

In step 401, a base station receives a random access preamble sent by aterminal, and sends a random access response to the terminal.

In step 402, the base station receives a first request message carryinguplink data sent by the terminal.

In an embodiment, after the base station receives the first requestmessage carrying the uplink data sent by the terminal, the methodfurther includes sending, by the base station, a second response messageto the terminal, where the second response message carries one or acombination of: a contention resolution identification; high-levelacknowledgement information for the uplink data; an uplink data sendingfailure indication; an uplink data retransmission indication; or userservice data.

In an embodiment, the first request message further carries at least oneor a combination of indication information of preferentially setting upan S1 interface; indication information of receiving high-levelacknowledgement information for the uplink data; terminal identificationinformation; information for identifying a mobility management entity(MME) at which the terminal registers; access stratum securityinformation; or a connection setting up reason corresponding to datatransmission.

In an embodiment, the method further includes steps 403 and 404.

In step 403, in response to determining that the first request messagecarries the indication information of preferentially setting up the S1interface, sending, by the base station, a first S1 interface messagecarrying the uplink data to a network side; and

In step 404, the base station receives a second S1 interface messagereturned by the network side, and in response to determining that thebase station acquires the high-level acknowledgement information fromthe second S1 interface message, sends the high-level acknowledgementinformation to the terminal.

In an embodiment, the method further includes: in response todetermining that the base station receives downlink data in the secondS1 interface message, sending, by the base station, the downlink data tothe terminal.

In an embodiment, the method further includes: sending, by the basestation, operation indication information to the terminal through asystem message or a dedicated message, where the operation indicationinformation is used for indicating the terminal a manner forre-performing random access after a random access failure.

The manner for re-performing the random access includes one of: changingpreferentially a coverage level and re-performing the random access;sending preferentially a random access preamble not for requesting anuplink data transmission resource or sending the random access preambleto re-perform the random access; and sending preferentially the firstrequest message carrying the radio resource control (RRC) message tore-perform the random access.

In an embodiment, the method further includes: in a case where theterminal is in a connected state and the first request message furthercarries an RRC message, and after receiving, by the base station, thefirst request message carrying the uplink data sent by the terminal,sending, by the base station, a second response message to the terminal,where the second response message further carries an RRC reset-upmessage.

In an embodiment, the method further includes: in a case where theterminal is in a connected state and the first request message furthercarries a request release indication, and after receiving, by the basestation, the first request message carrying the uplink data sent by theterminal, sending, by the base station, a second response message to theterminal, where the second response message further carries an RRCrelease message.

In an embodiment, the method further includes: sending, by the basestation, a data carrying determination threshold to the terminal througha system message or a dedicated message; where the data carryingdetermination threshold is used by the terminal to determine to selectthe random access preamble sent to the base station from whether arandom access preamble set not for requesting the uplink datatransmission resource or a random access preamble set for requesting theuplink data transmission resource, or the data carrying determinationthreshold is used by the terminal to determine to select a random accessresource for sending the random access preamble to the base station fromwhether a random access resource set for requesting the uplink datatransmission resource or a random access resource set not for requestingthe uplink data transmission resource; where the data carryingdetermination threshold includes: a data carrying threshold configuredfor all coverage levels, or a data carrying determination thresholdconfigured for each coverage level separately.

In an embodiment, the random access response carries indicationinformation for indicating a sending manner for the terminal to send thefirst request message; where receiving, by the base station, the firstrequest message carrying uplink data sent by the terminal includes: inresponse to determining that a second preset condition is satisfied,receiving, by the base station, the first request message carrying theuplink data sent by the terminal; and in response to determining that athird preset condition is satisfied, receiving, by the base station, thefirst request message carrying an RRC message sent by the terminal.

In an embodiment, satisfying the second preset condition is that theindication information is data amount information of a data size withuplink grant and the data size with the uplink grant is greater than anuplink grant threshold, or that the indication information indicates todirectly send the uplink data at the time of sending the first requestmessage; and satisfying the third preset condition is that theindication information is the information of the data size with theuplink grant and the data size with the uplink grant is less than orequal to the uplink grant threshold, or that the indication informationindicates to carry the RRC message at the time of sending the firstrequest message.

In an embodiment, the uplink grant threshold is an uplink grantthreshold corresponding to a state of the terminal before sending therandom access preamble; or an uplink grant threshold corresponding to acoverage level at which the terminal is located and the state of theterminal before sending the random access preamble, that is, the sameuplink grant threshold may be configured for multiple coverage levels,or different uplink grant thresholds may be configured for multiplecoverage levels separately.

In an embodiment, an uplink grant threshold corresponding to theterminal in a connected state is greater than an uplink grant thresholdcorresponding to the terminal in an idle state.

In an embodiment, in a case where the terminal is in an idle state andafter receiving, by the base station, the first request message carryingthe uplink data sent by the terminal, sending, by the base station, asecond response message to the terminal, where the second responsemessage further carries an RRC response message.

An embodiment of the present application provides a data transmissionmethod. The method includes sending a first request message to a basestation in a random access process in a case where the terminal is in anidle state, receiving a second response message sent by the basestation, and acquiring downlink data in the second response message.

An embodiment of the present application provides a data transmissionmethod. The method includes in a process of performing a random accessin a case where a terminal is in an idle state, receiving, by a basestation, a first request message sent by the terminal, in response todetermining that the base station has downlink data required to be sentto the terminal, carrying, by the base station, the downlink data at thetime of sending the second response message to the terminal.

In an embodiment, before the terminal in the idle state initiates therandom access, buffering the downlink data in response to determiningthat the base station receives the downlink data required to be sent tothe terminal sent by a network side.

An embodiment of the present application provides a data transmissionmethod. The method includes in a process of performing a random accessin a case where a terminal is in an idle state, sending, by a networkside, a second S1 interface message to a base station after receiving afirst S1 interface message sent by the base station, where the second S1interface message carries downlink data required to be sent to theterminal.

In an embodiment, the method further includes: before the terminal inthe idle state initiates the random access, buffering the downlink dataafter the network side receives the downlink data required to be sent tothe terminal sent by an application stratum.

An embodiment of the present application provides a data transmissionmethod. The method includes in a case where a terminal is in a connectedstate, receiving, by the terminal, a physical downlink control channelcommand sent by a base station, acquiring an non-competitive resourceallocated to the terminal by the base station from the physical downlinkcontrol channel command, initiating a random access by using a randomaccess preamble corresponding to the non-competitive resource; andreceiving, by the terminal, a random access response sent by the basestation, and in response to determining that the random access responsecarries indication information for simultaneously sending downlink data,receiving, by the terminal, the downlink data. An embodiment of thepresent application provides a data transmission method. The methodincludes in a case where a terminal is in a connected state, sending, bya base station, a physical downlink control channel command to theterminal, the physical downlink control channel command carries anon-competitive resource allocated by the base station to the terminal;and after receiving a random access initiated by the terminal using arandom access preamble corresponding to the non-competing resource,sending, by the base station, a random access response to the terminal,and the random access response carries indication information forsimultaneously sending downlink data, and sending the downlink datasimultaneously.

The present application is further described by the followingembodiments.

Embodiment One (a Basic Process of Sending Uplink Data in an Idle State,a Control Plane Scheme)

This embodiment provides an idle state uplink data transmission schemewithout state transfer. When a UE is in an RRC_IDLE state, the UE sendsa random access preamble for requesting a resource for sending uplinkdata. After receiving a random access response sent by the base stationand obtains uplink grant, the UE sends the uplink data to the basestation at the same time of sending a first request message. After theUE receives a second response message sent by the base station anddetermines that a contention is successfully resolved, the UE considersthat the uplink data is sent successfully, and the UE maintains theRRC_IDLE state. At the same time, the UE may regard a media accesscontrol (MAC) stratum identity temporary-radio network temporaryidentity (T-RNTI) allocated by the base station as a formal MAC stratumidentity cell-radio network temporary identify (C-RNTI), the UE in theRRC_IDLE state retains the C-RNTI for a first length of time which maybe preset or configured by a network side for the UE.

In this embodiment, the UE in the RRC_IDLE state uses a control plane(CP) scheme, as shown in FIG. 5 , which includes steps 501 to 507.

In step 501, when the UE is in the RRC_IDLE state, the UE sends a randomaccess preamble to a base station in a random access process forrequesting a resource for sending uplink data, i.e., requesting uplinkdata transmission resource.

In step 502, the base station sends a random access response to the UE.

The random access response carries a temporary MAC stratum identifyT-RNTI allocated by the base station to the UE.

In step 503, after receiving the random access response and obtainingthe uplink grant, the UE simultaneously sends uplink data to the basestation at the time of sending the first request message (Msg3).

The Msg3 may only carry an identity (such as a data target addressidentify) containing a core network identify and the uplink data,without an RRC message. The difference from the related art is that theMsg3 in the related art needs to carry the RRC message, such as an RRCconnection setup request message, an RRC connection resume requestmessage, or a new RRC connection public request message, which is usedfor triggering to setup or resume an RRC connection. In this embodiment,no RRC message is carried.

If the UE does not store a UE context at the time of releasing the RRCconnection last time (i.e., using the CP scheme), the UE should carry anidentity allocated by the core network to the UE, such as an S-TMSI, orinformation, such as the data target address identify or globally uniquemobility management entity identifier (GUMMEI) which is able to identifya mobility management entity (MME) attached to the UE to the basestation at the time of sending an uplink data packet through the Msg3.The UE may also carry access stratum security information, such asul-NAS-MAC or ul-NAS-Count, to the base station at the time of sendingthe uplink data packet, and the access stratum security information maybe obtained according to non-access stratum (NAS) security information.The Msg3 may also carry a connection setup reason, such as representinga connection setup reason for uplink data transmission.

The UE may include indication information of whether to set up an S1interface preferentially in the first request message (for example, ifthe UE considers that the uplink data needs a high-levelacknowledgement. In this case, it may be considered that the uplink datasent by the UE does not need a radio link control (RLC) and hybridautomatic repeat request (HARQ) stratum acknowledgement, just needs towait for the high-level acknowledgement. If the S1 interface needs to beset up preferentially, IND_needforS1=YES information may be carried, andthis indication may also be used as indication information of whetherthe UE needs to receive the high-level acknowledgement information ofthe uplink data.

In step 504, the base station sends a first SI interface messagecarrying the uplink data to a network side.

For example, the first S1 interface message is a data transmissionrequest (Data Transmission Req).

In other embodiments, the first S1 interface message may also be aninitial user equipment information message; a user equipment contextresume request message; an uplink non-access stratum transport message;or a path switch request message; or the first S1 interface message mayalso be other newly defined S1 interface messages. The network side is,such as, a mobility management entity (MME) attached to the UE.

If the UE also carries the access stratum security information to thebase station, the base station may also send the access stratum securityinformation to the MME at the same time.

In step 505, the network side sends a second S1 interface message to thebase station.

For example, the second S1 interface message is a data transmissionacknowledgement (Data Transmission Ack).

Or the second S1 interface message may also be a connection setupindication message; a UE context resume response message; a downlink NAStransport message; a path switch request acknowledgement message; or thesecond S1 interface message may also be another newly defined S1interface messages.

The second S1 interface message carries high-level acknowledgementinformation (acknowledgement/non-acknowledgement) of the uplink data,and may also include downlink access stratum security information.

In step 506, the base station sends a second response message (Msg4) toa terminal.

The second response message carries a contention resolution ID (such ascarried by a MAC stratum control unit).

The second response message (Msg4) may only carry the contentionresolution ID and not the RRC message.

The second response message carries the high-level acknowledgementinformation (Ack/Nack for UL data), or an uplink data retransmissionindication (DataResendIND).

In step 507, after receiving the second response message sent by thebase station and determining that the contention is successfullyresolved according to the contention resolution ID, the UE considersthat the uplink data is sent successfully this time and maintains theRRC_IDLE state.

In the related art, the base station first sends the second responsemessage to the terminal, and then sends the first S1 interface messageto the MME. The first S1 interface message usually triggers the basestation and the MME to set up the S1 interface and UE context for theUE.

Compared with the related art, in this embodiment, the first S1interface message may be sent before the second response messageaccording to the UE indication, and not trigger to set up the S1interface and the UE context for the UE.

In the related art, the Msg4 needs to carry an RRC message, such as theRRC connection setup message, the RRC connection resume message, or anew RRC connection public response message to complete the RRC setup orresume process. In this application, the Msg4 may not need to carry theRRC message.

In an embodiment, if the UE carries the indication of setting up the S1interface preferentially at the time of sending the uplink data packet,the UE and the base station need to use a prolonged contentionresolution timer. The prolonged contention resolution timer may bestatically configured or the base station broadcasts durations ofmultiple contention resolution timers in a system message. The UE andthe base station select one of them to use according to correspondingindication.

In an embodiment, the UE may regard the temporary MAC stratum identifyT-RNTI allocated by the base station as the formal MAC stratumidentifier C-RNTI in step 502. When maintaining the RRC_IDLE state, theUE retains the C-RNTI for a period of time. The specific retention timemay be preset or configured by the network side for the UE. During thistime, the UE always uses the C-RNTI to demodulate a physical channel ina calling search space (CSS) of the random access response (RAR), or ina newly defined CSS dedicated for Msg3 data transmission.

In an embodiment, if the UE receives the second response message of thebase station but determines contention resolution failure, or does notreceive the second response message, the UE considers uplink datasending failure, and the UE re-initiates a random access process totransmit data.

In an embodiment, if the second S1 interface message does not include anacknowledgement for the uplink data, or indicates uplink datatransmission failure, the base station may include an uplink datatransmission failure indication or an uplink data retransmissionindication in the second response message sent to the UE.

In an embodiment, if the UE receives the second response message of thebase station, the UE determines that the contention is resolvedsuccessfully according to the contention resolution ID, and thetemporary MAC stratum identify T-RNTI allocated by the UE base stationis regarded as the formal MAC stratum identify C-RNTI, but the secondresponse message includes the uplink data sending failure indication orthe uplink data retransmission indication, the UE needs to re-initiate arandom access process to transmit the data, and the Msg3 carries theC-RNTI.

Embodiment Two (a Basic Process of Sending Uplink Data in an Idle State,a User Plane Scheme)

In this embodiment, the UE is in the RRC_IDLE state. Compared with theembodiment one, this embodiment adopts a user plane (UP) scheme. Asshown in FIG. 6 , steps 601 to 607 are included.

In step 601, when the UE is in the RRC_IDLE state, the UE sends a randomaccess preamble to a base station in a random access process forrequesting a resource for sending uplink data.

In step 602, the UE receives a random access response sent by the basestation and obtains uplink grant.

In step 603, the UE sends uplink data to the base station at the time ofsending a first request message (Msg3) at the same time.

This embodiment adopts the UP scheme. The UE performed a suspendoperation at the time of releasing an RRC connection last time andstores a UE context and resume ID (ResumeID). The UE carries the resumeID at the same time of sending the uplink data through the Msg3.

The Msg3 may only carry an identity (such as a data target addressidentify or GUMMEI information) including a core network identify andthe uplink data, without an RRC message.

Compared with the related art, the Msg3 in the related art needs tocarry the RRC message, such as an RRC connection setup request message,an RRC connection resume request message, or a new RRC connection publicrequest message, which is used for triggering to setup or resume an RRCconnection. In this embodiment, no RRC message is carried.

The UE may also carry access stratum security information to the basestation at the time of sending an uplink data packet. The access stratumsecurity information may be obtained according to NAS securityinformation.

The UE may also carry a connection setup reason, such as representing aconnection setup reason for uplink data transmission.

The UE may include indication information of whether to set up an S1interface preferentially; (for example, if the UE considers that theuplink data needs a high-level acknowledgement, in this case, it mayalso considered that the uplink data sent by the UE does not need an RLCand HARQ stratum acknowledgement, just needs to wait for the high-levelacknowledgement). If the S1 interface needs to be set up preferentially,IND_needforS1=YES information is carried.

The indication may also be used as indication information of whether theUE needs to receive high-level acknowledgement information of the uplinkdata.

In step 604, the base station sends a first SI interface messagecarrying the uplink data to a network side.

For example, the first S1 interface message is a data transmissionrequest (Data Transmission Req).

The network side is, such as, a mobility management entity (MME)attached to the UE.

If the UE also carries the access stratum security information to thebase station, the base station may also send the access stratum securityinformation to the MME at the same time.

The base station finds the UE context stored on a base station sideaccording to a resume identify, and sends the first S1 interface messageto the MME according to MME information attached to the UE included inthe UE context.

In step 605, the network side sends a second S1 interface message to thebase station.

For example, the second S1 interface message is data transmissionacknowledgement, carries high-level acknowledgement information(acknowledgement/non-acknowledgement) of the uplink data, and may alsoinclude downlink access stratum security information.

In step 606, the base station sends a second response message (Msg4) toa terminal.

The second response message carries a contention resolution identify,such as, carried by an MAC stratum control unit.

The second response message (Msg4) may only carry the contentionresolution ID and not the RRC message.

In step 607, after receiving the second response message sent by thebase station and determining that the contention is successfullyresolved according to the contention resolution ID, the UE considersthat the uplink data is sent successfully this time and maintains theRRC_IDLE state.

Embodiment Three (Continuous Data Transmission in an Idle State)

A UE may not be able to transmit all data to be transmitted during aninitial random access process, in the RRC_IDLE state and a state havinga C-RNTI, the UE may continue to send the first request message carryingthe uplink data to a base station, and the base station sends a secondresponse message to the UE and carries an acknowledgement for the uplinkdata at the same time. This process may be interacted several timesuntil transmission of the data to be transmitted is completed.

As shown in FIG. 7 , steps 701 to 712 are included.

Steps 701 to 707 are the same as the steps 501 to 507, where the step703 may also carry a buffer area status report, indicating that there isdata to be sent.

In step 708, the base station allocates new uplink grant to a terminalthrough a physical downlink control channel (PDCCH) transmission, andthe PDCCH transmission is scrambled with a cell-radio network temporaryidentify (C-RNTI).

In step 709, the terminal uses the C-RNTI to demodulate the PDCCHtransmission, acquires the uplink grant, and sends the uplink data tothe base station by using the uplink grant.

In step 710, the base station sends a first SI interface messagecarrying the uplink data to a network side.

In step 711, the network side sends a second S1 interface message to thebase station.

In step 712, if the second S1 interface message includes theacknowledgement for the uplink data, the base station sends theacknowledgement for the uplink data to the terminal. Among them, steps708 to 712 may be repeatedly performed several times until thetransmission of all data to be transmitted of the terminal is completed.

Embodiment Four (Downlink Buffer Data is Sent in an Msg4, a CP Schemeand a UP Scheme are Combined)

If there is downlink data on a network side needed to be sent to an M2M,such as a narrow band Internet of Things (NB-IoT) or enhanced machinetype communication (eMTC) user, and if these data is delay tolerance,and then the network side may buffer these downlink data for a period oftime and then send it to the UE. During this period of time, if thenetwork side receives the first S1 interface message, the network sidemay send the buffered downlink data to the base station in the second S1interface message. If the base station has not sent a second responsemessage to the UE yet after receiving the second S1 interface message,the base station may send downlink data included in the second responsemessage to the UE, and the downlink data may be included in a newlydefined media access control control element (MAC CE), or a newlydefined data container information element (IE).

As shown in FIG. 8 , it is a downlink data transmission process for arandom access process, including steps 801 to 808.

In step 801, when the UE is in an RRC_IDLE state, the UE sends a randomaccess preamble to the base station in a random access process forrequesting a resource for sending uplink data.

In step 802, the UE receives a random access response sent by the basestation and obtains uplink grant.

In step 803, the UE sends uplink data to the base station at the time ofsending a first request message (Msg3) at the same time.

If the UE does not store a UE context at the time of releasing the RRCconnection last time (i.e., using the CP scheme), the UE should carry anidentity allocated by a core network to the UE, such as an S-TMSI, orinformation, such as a data target address identify or globally uniquemobility management entity identifier (GUMMEI) which is able to identifyan mobility management entity (MME) attached to the UE to the basestation at the time of sending an uplink data packet through an Msg3.The UE may also carry access stratum security information to the basestation at the time of sending an uplink data packet. The access stratumsecurity information may be obtained according to NAS securityinformation. Alternatively, the UE performed a suspend operation at thetime of releasing an RRC connection last time and stores a UE contextand resume ID (ResumeID). The UE carries the resume ID at the same timeof sending the uplink data through the Msg3.

In step 804, the base station checks whether there is downlink dataneeded to be sent to a terminal, and if yes, the downlink data isincluded in the second response message.

In step 805, the base station sends a first SI interface messagecarrying the uplink data to the network side.

For example, the first S1 interface message is a data transmissionrequest (Data Transmission Req).

The network side is, such as, a mobility management entity (MME)attached to the UE.

If the UE also carries the access stratum security information to thebase station, the base station may also send the access stratum securityinformation to the MME at the same time.

In step 806, the network side checks whether there is downlink dataneeded to be sent to a terminal, and if yes, the downlink data isincluded in the second S1 interface message.

In step 807, the network side sends the second S1 interface messagecarrying the downlink data to the base station.

For example, the second S1 interface message is a data transmissionacknowledgement (Data Transmission Ack).

For example, the second S1 interface message may also carry high-levelacknowledgement information (acknowledgement/non-acknowledgement) of theuplink data, and may also include downlink access stratum securityinformation.

In step 808, the base station sends the second response message (Msg4)carrying the downlink data to a terminal.

Other information carried in the second response message may refer tothe step 506.

Embodiment Five (Downlink Data Buffer)

If a network side has downlink data to be sent to an M2M (NB-IoT oreMTC) user and the user is in an S1 interface idle state, and if thesedata is delay tolerance, then the network side may buffer these downlinkdata for a period of time without triggering to send an S1 interfacepaging message. Or if the network side has downlink data to be sent tothe M2M (NB-IoT or eMTC) user and the user is in an S1 interfaceconnected state, the network side sends the data to a base station.However, at this time, a terminal may be in an air interface idle state,so the base station may buffer these downlink data for a period of timewithout triggering to send an air interface paging message.

As shown in FIG. 9 , it is a downlink data buffering flowchart,including steps 901 to 904.

In step 901, an application stratum sends downlink data to the networkside.

In step 902, the network side determines that the user is in the S1interface idle state and these downlink data is delay tolerance, thenthe network side may buffer the downlink data for a period of timewithout triggering to send the S1 interface paging message. A bufferduration may be a preset value.

In step 903, the network side determines that the user is in the S1interface connected state, and sends the downlink data to the basestation.

In step 904, the base station determines that the terminal is in the airinterface idle state and these downlink data is delay tolerance, thenthe base station may buffer these downlink data for a period of timewithout triggering to send the air interface paging message. A bufferduration may be a preset value.

FIG. 10 is another implementation mode of the embodiment one or theembodiment two. This embodiment includes steps 1001 to 1009.

In step 1001, when the UE is in an RRC_IDLE state, the UE sends a randomaccess preamble to a base station in a random access process forrequesting a resource for sending uplink data.

In step 1002, the UE receives a random access response sent by the basestation and obtains uplink grant.

In step 1003, the UE sends uplink data to the base station at the timeof sending a first request message (Msg3) at the same time.

The Msg3 may carry a terminal identify, such as an S-TMSI or a resumeidentify, and may also carry an identity (such as GUMMEI information ora data target address identify) of a core network registered by theterminal and uplink data, without carrying an RRC message.

The UE may also carry access stratum security information to the basestation at the time of sending an uplink data packet. The access stratumsecurity information may be obtained according to NAS securityinformation. The UE may also carry a connection setup reason.

In step 1004, the base station sends a second response message (Msg4) toa terminal.

The second response message carries a contention resolution identify,such as, carried by an MAC stratum control unit.

The second response message (Msg4) may only carry the contentionresolution ID and not the RRC message.

In step 1005, after the UE receives the second response message sent bythe base station and determines that the contention is resolvedsuccessfully according to the contention resolution ID, the UE maintainsthe RRC_IDLE state, and takes a temporary-radio network temporaryidentity (T-RNTI) allocated by the base station as a cell-radio networktemporary identity (C-RNTI), and retains the C-RNTI for a first lengthof time.

In step 1006, the base station sends a first SI interface messagecarrying the uplink data to a network side.

For example, the first S1 interface message is a data transmissionrequest (Data Transmission Req).

In step 1007, the network side sends a second S1 interface message tothe base station.

For example, the second S1 interface message is data transmissionacknowledgement, carries high-level acknowledgement information(acknowledgement/non-acknowledgement) of the uplink data.

In step 1008, the base station sends downlink assignment information tothe terminal through a PDCCH transmission, and the PDCCH transmission isscrambled with the C-RNTI.

In step 1009, the terminal uses the C-RNTI to demodulate the PDCCHtransmission, acquires the downlink assignment information, and use thedownlink assignment information to receive downlink data sent by thebase station to the terminal. The downlink data may be high-levelacknowledgement information of the uplink data.

Embodiment Six (a Terminal Determines an Msg3 Sending Manner Accordingto Information in an RAR (with Data or an RRC Message, a CP Scheme and aUP Scheme are Combined)

When a UE is in an RRC_IDLE state, the UE sends a random access preamblefor requesting a resource for sending uplink data in a random accessprocess. The base station controls whether to setup or resume an RRCconnection for the UE and whether to transfer the UE in an RRC_CONNECTEDstate.

The base station carries an indication in a random access response,which is used for indicating a sending manner of a first requestmessage.

The indication may be an implicit indication, such as data amountinformation of a data size included in uplink grant, such as a transportblock size (TB size) in a UL grant field in the RAR messages. When theindication (such as data amount information of the data size with theuplink grant) exceeds a certain threshold (hereinafter referred to as anuplink authorization threshold), the UE sends the uplink data directlyto the base station at the time of sending the first request message.When the UE sends the first request message, the UE should encapsulatethe uplink data according to the data amount information of the datasize with the uplink grant and send the uplink data to the base station.If the UE's data to be sent exceeds the data amount information of thedata size with the uplink grant, the UE may split the data to be sentaccording to the data amount information of the data size with theuplink grant into multiple fragments and sent in sequence. If theindication (such as the data amount information of the data size withthe uplink grant) does not exceed an uplink grant threshold, the UEsends the first request message to the base station, and the firstrequest message carries an RRC message, and the RRC message may be anRRC connection setup request or an RRC connection resume requestmessage, or an RRC connection public request message.

Alternatively, the indication may be an explicit indication, indicatingthe UE to directly send the uplink data at the time of sending the firstrequest message, or indicating the UE to initiate an ordinary RRCconnection setup or resume process.

The uplink grant threshold may be a statically configured preset valueor be configured by the base station. For example, the uplink grantthreshold is sent to the UE through a newly defined field in a systemmessage, and may be dynamically adjusted. For example, the uplink grantthreshold is configured to be 200 bits. In an embodiment, the uplinkgrant threshold may be individually configured for each coverage level.

Or the base station may assign appropriate uplink grant to the terminalin the random access response according to a terminal request at thetime of carrying another piece of indication information. The indicationinformation indicates that if the UE fails to directly send the uplinkdata at the time of sending the first request message this time, the UEshould use a random access preamble or a random access resource notrequesting for sending the uplink data at the time of reinitiating therandom access subsequently, i.e., the UE should initiate a random accessfor the ordinary RRC connection setup or resume process.

FIG. 11 is an implementation of directly sending the uplink data to thebase station of the UE at the time of sending the first request message.As shown in FIG. 11 , the UE is in an RRC_IDLE state, including steps1100 to 1106.

In step 1100, the base station sends the uplink grant threshold(T_ULgrant) through the system message.

In step 1101, the UE sends a random access preamble to a base station ina random access process for requesting a resource for sending uplinkdata.

In step 1102, the base station sends the random access response to theUE, and carries larger uplink grant.

In step 1103, the UE determines that the data size with the uplink grantis greater than the uplink grant threshold, and the UE sends the uplinkdata to the base station at the time of sending the first requestmessage (Msg3).

This embodiment adopts the UP scheme. The UE performed a suspendoperation at the time of releasing an RRC connection last time andstores a UE context and resume ID (ResumeID). The UE carries the resumeID at the same time of sending the uplink data through the Msg3. If theCP scheme is adopted, the UE should carry an identity allocated to theUE by a core network, such as an S-TMSI, or information, such as GUMMEIinformation, which is able to identify an MME attached to the UE, to thebase station.

In step 1104, the base station sends a first SI interface messagecarrying the uplink data to a network side.

In step 1105, the network side sends a second S1 interface message tothe base station.

In step 1106, the base station sends a second response message (Msg4) toa terminal.

If the indication in the random access response (such as the data amountinformation of the data size with the uplink grant) does not exceed theuplink grant threshold, the UE sends the first request message to thebase station, and the first request message carries the RRC message, andthe UE should setup or resume the RRC connection after receiving thesecond response message carrying the RRC message, and transfer in theRRC_CONNECTED state, as shown in FIG. 12 , including steps 1200 to 1208.

In step 1200, the base station sends the uplink grant threshold(T_ULgrant) through the system message.

In step 1201, the UE sends a random access preamble to a base station ina random access process for requesting a resource for sending uplinkdata.

In step 1202, the base station sends the random access response to theUE, carries data amount information of a small data size with the uplinkgrant (not exceeding the uplink grant threshold).

In step 1203, the UE determines that the data size with the uplink grantis less than or equal to the uplink grant threshold, and the UE sendsthe first request message (Msg3) to the base station, carries the RRCconnection public request message; the public request message may be anexisting RRC connection request message, the RRC connection resumerequest message, or the newly defined RRC connection public requestmessage.

The Msg3 message also carries the identify allocated to the UE by thecore network, such as the S-TMSI, or information which is able toidentify the MME attached to the UE, to the base station or carry theresume ID.

In step 1204, the base station sends the first S1 interface message tothe network side. In step 1205, the network side sends a second S1interface message to the base station.

In step 1206, the base station sends the second response message (Msg4)to the terminal, carries an RRC connection public response message. Thepublic response message may be an existing RRC connection setup message,the RRC connection resume message, or the newly defined RRC connectionpublic response message.

In step 1207, the UE sets up an RRC connection and enters theRRC_CONNECTED state.

In step 1208, the UE sends an Msg5 message to the base station, andcarries the uplink data.

Embodiment Seven (a Terminal May Process Msg4+RRC Messages after SendingMsg3+ Data

Even if a base station does not receive an RRC connection setup requestor an RRC resume request message in a first request message, the basestation may still actively send RRC to initiate an RRC connection setupor resume process, and transfer the terminal to an RRC_CONNECTED state,i.e., the base station sends a second response message carrying an RRCmessage to the UE. The RRC message may be an RRC connection setup,resume or public response message. When receiving the second responsemessage, the UE should setup or resume an RRC connection and transfer tothe RRC_CONNECTED state.

In the related art, generally the UE needs to send an RRC requestmessage before receiving an RRC response message. The RRC requestmessage may be an RRC connection setup request message, an RRCconnection resume request message, or a new RRC connection publicrequest message. The RRC response message may be the RRC connectionsetup message, the RRC connection resume message, or a new RRCconnection public response message. In this embodiment, even if the UEhas not sent the RRC request message, and may also process the RRCresponse message.

As shown in FIG. 13 , steps 1300 to 1308 are included.

In step 1300, the base station sends an uplink grant threshold(T_ULgrant) through a system message.

In step 1301, the UE sends a random access preamble to the base stationin a random access process for requesting a resource for sending uplinkdata.

In step 1302, the base station sends a random access response to the UE.

In step 1003, the UE sends uplink data to the base station at the timeof sending a first request message (Msg3) at the same time.

The UE should carry an identity allocated to the UE by a core networksuch as an S-TMSI, or information which is able to identify an MMEattached to the UE, to the base station or carry a resume ID at the timeof sending an uplink data packet through the Msg3.

In step 1304, the base station sends a first SI interface messagecarrying the uplink data to a network side.

In step 1305, the network side sends a second S1 interface message tothe base station.

In step 1306, the base station sends the second response message (Msg4)to the base station, carries an RRC connection public response message.The public response message may be an existing RRC connection setupmessage, the RRC connection resume message, or the newly defined RRCconnection public response message.

In step 1307, the UE sets up an RRC connection and enters theRRC_CONNECTED state.

In step 1308, the UE sends an Msg5 to the base station.

Embodiment Eight

In a certain coverage level, if the UE fails to send uplink data (anMsg3 in a first format) for a certain number of times at the same timeof sending a first request message, the UE preferentially changes thecoverage level. When the coverage level reaches the maximum, the UE thenturns to attempt to send the first request message carrying an RRCmessage to setup or resume an RRC connection (the Msg3 in a secondformat). Or at a certain coverage level, if the UE fails to send theuplink data (in the first format) at the same time of sending the firstrequest message for a certain number of times, the UE preferentiallychanges to attempt to send the first request message carrying the RRCmessage to setup or resume the RRC connection (the Msg3 in the secondformat). If the UE still fails, the UE directly selects a next coveragelevel after a number of failures is reached according to a configurednumber of failures. At a new coverage level, the UE still performs arandom access attempt in the above order.

The base station may broadcast operation indication information in asystem message. If the UE is indicated to change the coverage levelpreferentially, the UE may be indicated a number of attempts of usingthe Msg3 in the second format at the maximum coverage level, or beindicated whether the number of attempts is the same as the number ofattempts of using the Msg3 in the second format. If the UE is indicatedto change to attempt the Msg3 in another format preferentially, the UEmay be indicated the number of attempts of using the Msg3 in each formatat the current coverage level, or be indicated a proportion of thenumber of attempts of using the Msg3 in each format in a total number ofattempts.

At a certain coverage level, if there is a power raising operation, theUE may terminate or suspend the power raising operation in advance eachtime a random access is performed. For example, the UE first determineswhether an Msg3 format used this time is the same as that used in thelast time, and determines whether to terminate or suspend the powerraising operation in advance according to the determination result. Anexample of adjusting the power raising operation is as follows.

If the different Msg3 format is used from the last time, no power israised, or if the different Msg3 format is used from the last time, andthe last time uses the Msg3 in the first format, and this time uses theMsg3 in the second format, no power is raised. That is, the powerraising process is suspended or terminated in advance.

Or, the UE determines whether to terminate or suspend the power raisingoperation in advance according to a reason for an access attempt failurelast time. Another example of adjusting the power raising operation isas follows.

After the UE fails to attempt the Msg3 in the first format, the UEdetermines whether to terminate or suspend the power raising process inadvance according to the failure reason. If a certain type of failurereason occurs (such as a contention resolution failure), the UE does notincrease an uplink transmit power but simply attempts again.

When the UE is in an RRC_IDLE state, the UE sends a random accesspreamble for requesting a resource for sending uplink data in a randomaccess process. After the UE obtains uplink grant, the UE directly sendsthe uplink data to the base station at the time of sending the firstrequest message in the random access process.

When the UE sends the random access preamble selected in a random accesspreamble set P1 for requesting an uplink data transmission resource atthe current coverage level, but because a second response message (thesecond response message should include larger UL grant so that the UEsends uplink data without state transfer at the same time of sending thefirst request message) sent by the base station, or the contentionresolution fails in a subsequent process, this random access attemptfails, the UE needs to initiate random access process again. In thiscase, the UE needs to repeatedly send the random access preambles in P1.When the repeated sending reaches a certain number of times N1, thenumber of times N1 is a preset value corresponding to the currentcoverage level or configured by the network side for the UE, the UEstarts to use the random access preamble in the random access preambleset P2 not for requesting the uplink data transmission resource. Ifafter sending the random access preamble in P2, this random accessattempt fails because the second response message (the second responsemessage should include smaller UL grant so that the UE sends the firstrequest message including the RRC message to setup or resume the RRCconnection) sent by the base station or the contention resolution failsin the subsequent process, then the UE repeatedly sends the randomaccess preambles in P2. When the repeated sending reaches a certainnumber of times N2, the number of times N2 is a preset valuecorresponding to the current coverage level or configured by the networkside for the UE, and the UE skips to a next coverage level and repeatsthe process again.

When the terminal uses the random access preamble set P1 for the randomaccess, if the random access attempt fails because no random accessresponse is received, the UE marks a failure reason S1, and if therandom access attempt fails due to the contention resolution failure inthe subsequent process, the UE marks a failure reason S2. When the UEfails due to S1, and the terminal uses the random access preambles in P1for the random access again, the uplink transmit power may be increasedaccording to configuration parameters. However, when the UE fails due toS2, there may be multiple UEs attempting to send the uplink data at thetime of sending the first request message, and the system is overloaded.In this case, if the transmit power is still increased duringretransmission, the system contention may be intensified, so that in anext attempt, the UE does not increase the uplink transmit power butonly attempts again.

Embodiment Nine (Parallel Uplink Data Transmission and RRC ConnectionRe-Setup Process)

When a UE is in an RRC_CONNECTED state, an RRC re-set up process may betriggered due to a reason such as RLF. When the RRC is re-setup, theremay be uplink data to be transmitted or re-transmitted. In this case,the uplink data may be sent at the same time of re-setting up, i.e.,performing parallel uplink data transmission and RRC connection re-setup process.

As shown in FIG. 14 , the UE is in the RRC_CONNECTED state and uses a CPscheme to transmit the uplink data in a random access process, includingsteps 1406 to 1406.

In step 1401, the UE sends a random access preamble to the base stationin the random access process for requesting a resource for sendinguplink data.

In step 1402, the base station sends a random access response to the UE.

In step 1403, the UE sends a first request message (Msg3) to the basestation, carries an RRC connection public request message and uplinkdata; the RRC connection public request message may be an existing RRCconnection re-set up request message, or anew RRC connection publicrequest message.

The Msg3 also carries an identity allocated by a core network to the UE,such as an S-TMSI, or information, such as GUMMEI, which is able toidentify a mobility management entity (MME) attached to the UE to thebase station.

In step 1404, the base station sends a first SI interface messagecarrying the uplink data to a network side.

In step 1405, the network side sends a second S1 interface message tothe base station.

In step 1406, the base station sends the second response message (Msg4)to the terminal, carries an RRC connection public response message. TheRRC connection public response message may be the existing RRCconnection re-set up message or the new RRC connection public responsemessage.

As shown in FIG. 15 , a UP scheme is used for transmitting the uplinkdata in the random access process, including steps 1501 to 1506.

In step 1501, the UE sends the random access preamble to the basestation in the random access process for requesting a resource forsending uplink data.

In step 1502, the base station sends a random access response to the UE.

In step 1503, the UE sends a first request message (Msg3) to the basestation, carries an RRC connection public request message and uplinkdata; the RRC connection public request message may be an existing RRCconnection re-set up request message, or anew RRC connection publicrequest message.

The Msg3 also carries a Reestablish-UE ID

In step 1504, the base station sends a first SI interface messagecarrying the uplink data to the network side.

In step 1505, the network side sends a second S1 interface message tothe base station.

In step 1506, the base station sends the second response message (Msg4)to the terminal, carries an RRC connection public response message. TheRRC connection public response message may be the existing RRCconnection re-set up message or the new RRC connection public responsemessage.

Embodiment Ten (Quick Release after Sending Uplink Data in a ConnectedState)

When a UE is in an RRC_CONNECTED state, there is data needed to be sent,and the UE is out of synchronization or has no uplink resources, the UEneeds to initiate a random access process.

If the UE sends a random access preamble for requesting an resource forsending the uplink data, and the UE receives the random access responsesent by the base station and obtains sufficient uplink grant, it may beconsidered that the UE and the base station negotiate to complete thedata transmission as soon as possible and may initiate RRC connectionquick release, the UE simultaneously sends the uplink data to the basestation at the time of sending a first request message.

If the UE sends a random access preamble not for requesting the resourcefor sending the uplink data, or the UE does not obtain sufficient uplinkgrant from the base station, it may be considered that the UE sends anordinary preamble, and then triggers a complete RRC connection setupprocess, and the data is transmitted after the connection setup iscompleted.

After the UE sends the first request message and the uplink data, if theUE receives a second response message sent by the base station anddetermines that the contention is successfully resolved, the UEautonomously releases to an RRC_IDLE state.

When sending the first request message and the uplink data, the UE maycarry a release request indication, such as BSR=0, indicating that thebase station may release. After receiving the first request message andthe uplink data, the base station may trigger the quick release, andcarry an RRC release message in the second response message sent by thebase station to the UE, the release message is sent in a radio linkcontrol acknowledged mode (RLC AM). After receiving the second responsemessage, the UE first determines that the contention is successfullyresolved, then processes the RRC release message and sends anacknowledgement (ACK) to the message, and then the base station sends anRRC connection release message to the UE, and the UE is released to theRRC_IDLE state. If the contention resolution fails, the UE does notprocess the RRC message carried in the second response message. Comparedwith the related art, the RRC release messages in the related art mayonly be sent through an SRB1, and the RRC release messages in thepresent application may be sent through an SRB0.

The base station broadcasts different uplink grant thresholds for theidle state and the connected state through the system message. Theconnected state should have a stricter uplink grant threshold, i.e., theuplink grant threshold should ensure that when the UE initiates therandom access to transmit the data in the connected state, All the datato be transmitted should be transmitted once as soon as possible and theconnection should be released. The uplink grant threshold in theconnected state is larger than the uplink grant threshold in the idlestate.

As shown in FIG. 16 , steps 1601 to 1607 are included.

In step 1601, the UE sends the random access preamble to the basestation in the random access process for requesting resources forsending uplink data.

In step 1602, the base station sends a random access response to the UE.

In step 1603, the UE sends the first request message (Msg3) carrying theuplink data to the base station, and carries the release requestindication, such as BSR=0.

The Msg3 also carries a C-RNTI.

In step 1604, the base station sends a first SI interface messagecarrying the uplink data to the network side.

In step 1605, the network side sends a second S1 interface message tothe base station.

In step 1606, the base station sends the second response message (Msg4)to the terminal, carries an RRC connection release message.

In step 1607, the UE first processes the Msg4, then processes theconnection release message, and then the UE releases to the RRC_IDLEstate.

Embodiment Eleven (Non-Competitive Access Msg2 Carries Downlink Data)

When a UE is in an RRC_CONNECTED state, if a network side has downlinkdata to send to the UE but finds that the UE is in a non-synchronizationstate, a base station needs to send a PDCCH order to the UE to trigger arandom access process.

The PDCCH order includes an non-competitive resource allocated by thebase station to the UE. When the UE initiates a random access using arandom access preamble corresponding to the non-competitive resource,the base station finds information about the UE, and the base stationsends a random access response to the UE. The random access responseincludes an indication that indicates to send the downlink data to theUE at the same time. The UE uses received downlink grant to receive thedownlink data. After that, the UE may send a first request message tothe base station, which includes a acknowledgment for the receiveddownlink data. The UE needs to process tracking area (TA) informationfirst, completes a synchronization process, and then processes adownlink data packet.

As shown in FIG. 17 , the UE is in the RRC_CONNECTED state, includingsteps 1701 to 1706.

In step 1700, a network side sends the downlink data to the basestation.

In step 1701, the base station sends a PDCCH order to the UE, carriesthe non-competitive resource allocated by the base station to the UE.

In step 1702, the UE sends the random access preamble corresponding tothe non-competitive resource to the base station.

In step 1703, the base station sends a random access response to the UE,and simultaneously sends the downlink data, and the random accessresponse carries indication information to indicate to simultaneouslysend the downlink data.

In step 1704, after receiving the random access response, and using thereceived downlink data, the UE sends the first request message (Msg3) tothe base station, and carries acknowledgement information of thedownlink data.

In step 1705, the base station sends a first SI interface message to thenetwork side, and carries acknowledgement information of the downlinkdata.

In step 1706, the network side sends a second S1 interface message tothe base station.

Embodiment Twelve

When a UE is in an RRC_IDLE state, the UE sends a random access preamblefor requesting a resource for sending uplink data in a random accessprocess. The UE determines whether to request the resource for sendingthe uplink data in the following manner.

The base station configures a data carrying determination thresholdT_ULdataRA for each coverage level. When the UL data to be transmittedbuffered by the UE is greater than or equal to the data carryingdetermination threshold, the UE selects a random access preamble fromthe random access preamble set P1 for requesting the uplink datatransmission resource. When the UL data to be transmitted buffered bythe UE is less than the data carrying determination threshold, the UEselects a random access preamble from the random access preamble set P2not for requesting the uplink data transmission resource.

P1 and P2 are divided in the following manners.

Manner 1: a resource not belonging to a PRACH resource configured foreach coverage level is selected as P1.

For example, the base station configures at least one set of datatransmission physical resource block (PRB) resources for an R15 UE. AllPRBs which are different from physical random access channels/pagingphysical resource blocks (PRACHs/paging PRBs) configured for an R14 UEare taken as P1, in this case, all PRACHs/paging PRBs configured for theR14 UE may be regarded as P2. When multiple groups of data transmissionPRB resources are configured, each group of data transmission PRBresources is used for indicating a certain uplink data size requirement.For example, three sets of data transmission PRB resources areconfigured, which are identified as a group A, a group B, and a group Crespectively. Each set of data transmission PRB resources includes atleast one PRB. When the UE selects any PRB in the group A, it indicatesthat the UE requests for sending uplink data with a size between[DataSizeMinGroupA, DataSizeMaxGroupA] when sending the first requestmessage; each PRB may divide a PRACH time domain and a subcarrierresource for different coverage levels.

The base station configures all subcarriers not configured for the R14UE as P1 for the R15 UE, and the PRACH resource of each coverage levelconfigured for the R15 UE no longer includes the subcarrier resource. Atthis time, the subcarrier configured for the R14 UE may be regarded asP2. The subcarrier in P1 may be divided into at least one group of datatransmission subcarrier resources. Three groups of data transmissionsubcarrier resources are configured and identified as a group A, a groupB, and a group C respectively. Each set of data transmission subcarrierresources includes at least one subcarrier. When the UE selects anysubcarrier in the group A, it indicates that the UE requests for sendinguplink data with a size between [DataSizeMinGroupA, DataSizeMaxGroupA]when sending the first request message; when the R15 UE needs to selectthe PRACH resource corresponding to the coverage level at which the R15UE is located after selecting the subcarrier. As shown in FIG. 18 ,CE1_CBRA_S identifies a non-competitive random access resourcetransmitting the Msg3 in a single-tone mode at a coverage level 1 inFIG. 18 , CE1_CBRA_M identifies a non-competitive random access resourcetransmitting the Msg3 in a multi-tone mode at the coverage level 1 andCE1_CFRA identifies a non-competitive resource at the coverage level1.CE2_CBRA identifies all competitive random access resources at acoverage level 2, and CE2_CFRA identifies non-competitive resources atthe coverage level 2.CE3_CBRA identifies all competitive random accessresources at a coverage level 3, and CE3_CFRA identifies non-competitiveresources at the coverage level 3.

Manner 2: a certain resource belonging to the physical random accesschannel (PRACH) resource configured for each coverage level is selectedas P1.

For example, the base station divides unused subcarrier resources in thenon-competitive resource at each coverage level into at least one groupof data transmission subcarrier resources.

Although in the parameter configuration of R14, the non-competitiveresources calculated by(nprach-NumSubcarriers−nprach-NumCBRA-StartSubcarriers) should be aperiod of continuous values, but according to R14 technologies, the UEand the terminal use a mod operation to ensure that the UE still usessubcarriers that the base station may be learned after changing thecoverage level, so the actual used non-competitive subcarriers arediscontinuous.

Therefore, the base station may configure the unused subcarrierresources in the non-competitive resources at each coverage level asP1_CE1. As shown in FIG. 19 , CE1_CBRA_S identifies the a competitiverandom access resource transmitting the Msg3 in the single-tone mode atthe coverage level 1 in FIG. 19 , CE1_CBRA_S identifies the competitiverandom access resource transmitting the Msg3 in the multi-tone mode atthe coverage level 1 and CE1_CFRA identifies the non-competitiveresource at the coverage level 1. CE1_CFRA_A1˜CE1_CFRA_A3 respectivelyidentify resources which have not been configured for the existingterminals in the non-competitive resource at the coverage level 1, andmay be configured to be the random access resource for requesting theuplink data transmission resource used for the coverage level 1.CE2_CBRA identifies all competitive resources of the coverage level 2.CE2_CBRA identifies all non-competitive resources of the coverage level2. CE3_CBRA_S identifies the a competitive random access resourcetransmitting the Msg3 in the single-tone mode at the coverage level 3,CE3_CBRA_M identifies the competitive random access resourcetransmitting the Msg3 in the multi-tone mode at the coverage level 3 andCE3_CFRA identifies the non-competitive resource at the coverage level3. P1 for all CEs (P1_CE1) identifies resources which have not beenconfigured for the existing terminals in all subcarrier resources, andmay be configured to be the random access resource for requesting theuplink data transmission resource used for all coverage levels. In anembodiment, a sum of the random access resources used for requesting theuplink data transmission resource at all coverage levels is:P1=P1_CE1+P1_CE2+P1_CE3.

If there is no unused subcarrier resource in the non-competitiveresource at each coverage level, the base station can configure thenon-competitive resource at each coverage level as P1 for the R15 UE,provided that the base station is able to distinguish the random accessinitiated by the UE in the connected state and the idle state throughthe implementation mode. As shown in FIG. 20 , CE1_CBRA_S identifies thea competitive random access resource transmitting the Msg3 in thesingle-tone mode at the coverage level 1 in FIG. 20 , CE1_CBRA_Midentifies the competitive random access resource transmitting the Msg3in the multi-tone mode at the coverage level 1 and CE1_CFRA identifiesthe non-competitive resource at the coverage level 1.CE1_CFRA_A1˜CE1_CFRA_A3 respectively identify part of thenon-competitive resources at the coverage level 1. These resources havebeen configured for the existing terminals. If the base station maydistinguish between existing terminals and new terminals, theseresources may be allocated as the random access resources for requestingthe uplink data transmission resource used for the coverage level 1.CE2_CBRA identifies all competitive random access resources at thecoverage level 2. CE2_CBRA identifies all non-competitive resources ofthe coverage level 2. CE3_CBRA_S identifies the a competitive randomaccess resource transmitting the Msg3 in the single-tone mode at thecoverage level 3, CE3_CBRA_M identifies the competitive random accessresource transmitting the Msg3 in the multi-tone mode at the coveragelevel 3 and CE3_CFRA identifies the non-competitive resource at thecoverage level 3.

The base station divides subcarrier resources configured for theMulti-tone Msg3 in the competitive resource at each coverage level intoat least one group of data transmission subcarrier resources. As shownin FIG. 21 , CE1_CBRA_S identifies the a competitive random accessresource transmitting the Msg3 in the single-tone mode at the coveragelevel 1 in FIG. 21 , CE1_CBRA_M identifies the competitive random accessresource transmitting the Msg3 in the multi-tone mode at the coveragelevel 1 and CE1_CFRA identifies the non-competitive resource at thecoverage level 1. CE2_CBRA identifies all competitive random accessresources at a coverage level 2, and CE2_CFRA identifies non-competitiveresources at the coverage level 2. CE3_CBRA_S identifies the acompetitive random access resource transmitting the Msg3 in thesingle-tone mode at the coverage level 3, CE3_CBRA_M identifies thecompetitive random access resource transmitting the Msg3 in themulti-tone mode at the coverage level 1. CE3_CFRA identifies allnon-competitive resources of the coverage level 3.CE3_CBRA_A1˜CE3_CBRA_A3 indicates that some resources are configuredfrom CE3_CBRA_M to identify the random access resource for requestingthe uplink data transmission resource used for the coverage level 3.

Only UEs that support multi-tone Msg3 transmission are allowed to sendthe uplink data at the time of sending the first request message.

An embodiment of the present application provides a data transmissionapparatus. The apparatus includes a memory and a processor, where thememory stores a program and the data transmission method described inany one of the preceding embodiments is performed when the program isread and executed by the processor.

An embodiment of the present application provides a computer-readablestorage medium storing at least one program. The at least one program isexecutable by at least one processor, to perform the data transmissionmethod mentioned above.

The computer-readable storage medium includes a U disk, a Read-OnlyMemory (ROM), a Random Access Memory (RAM), a mobile hard disk, amagnetic disk, an optical disk or a plurality of media capable ofstoring program codes.

What is claimed is:
 1. A data transmission method, comprising: in a casewhere a terminal is in a connected state, receiving, by the terminal, aphysical downlink control channel command sent by a base station,acquiring an non-competitive resource allocated to the terminal by thebase station from the physical downlink control channel command,initiating a random access by using a random access preamblecorresponding to the non-competitive resource; and receiving, by theterminal, a random access response sent by the base station, and inresponse to determining that the random access response carriesindication information for simultaneously sending downlink data,receiving, by the terminal, the downlink data.
 2. A data transmissionapparatus, comprising a memory and a processor, wherein the memorystores a program which, when read and executed by the processor, causesthe processor to: in a case where a terminal is in a connected state,receive, by the terminal, a physical downlink control channel commandsent by a base station, acquire an non-competitive resource allocated tothe terminal by the base station from the physical downlink controlchannel command, initiate a random access by using a random accesspreamble corresponding to the non-competitive resource; and receive, bythe terminal, a random access response sent by the base station, and inresponse to determining that the random access response carriesindication information for simultaneously sending downlink data, receivethe downlink data.
 3. A data transmission method, comprising: in a casewhere a terminal is in a connected state, sending, by a base station, aphysical downlink control channel command to the terminal, the physicaldownlink control channel command carries a non-competitive resourceallocated by the base station to the terminal; and after receiving arandom access initiated by the terminal using a random access preamblecorresponding to the non-competing resource, sending, by the basestation, a random access response to the terminal, and the random accessresponse carries indication information for simultaneously sendingdownlink data, and sending the downlink data simultaneously.
 4. Anon-transitory computer-readable storage medium, comprising storedprograms, wherein the programs, when executed by a processor, performthe data transmission method of claim 1.